feat: update action runtime to node24#294
Conversation
|
I guess that another warning to anyone using action from personal github actions as they add a dependency on a single person. Last change on this repo was merged years ago. |
|
@ssbarnea Totally agree, dependency on personal projects is risky. In my job I also try to avoid it. Or at least use an internal fork to avoid potential supply chain attacks. Anyway, it's a shame and missed opportunity on my side I just couldn't find time for this project for so long. But I really can't ignore the upcoming deprecation of Node 24. @saschabratton Thanks for you contribution, merging this now. |
|
Thank you @dorny! 🙏🏻 If you have a moment to add a new version tag after merging this, I think you will also please a number of folks waiting for the |
|
Thanks dorny! My org has 51 repos using paths-filter and 7 repos using test-reporter, so your compatibility bump is much anticipated 🙏 |
|
@dorny can you release this please |
|
Released as v4.0.0 |
github-actions(deps): Bump dorny/paths-filter from 3.0.2 to 4.0.1
v4.0.0 is exactly the node24 update (dorny/paths-filter#294), so the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 workaround and its deprecation warning both go away. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
5 participants
GitHub is deprecating Node 20 for Actions runners, with Node 24 becoming the default on June 2, 2026. This updates the action runtime to
node24to stay ahead of the cutoff.This PR:
node20tonode24@types/nodeto^24.0.0and engines field to>= 24actions/checkout@v6andactions/setup-node@v6No functional changes — all inputs, outputs, and behavior remain identical.
Resolves #286